ITSM-1219: Implement pipelines for publishing libs#23
Merged
Conversation
- project: sdk-core 0.1.1-pipeline-test-0.0
- project: sdk-core 0.1.1-pipeline-test.0
dm3ch
force-pushed
the
chore/finish-pipelines
branch
from
46f306a to
c97aeaf
Compare
- project: sdk-core 0.1.1-pipeline-test.1
- project: sdk-core 0.1.1-pipeline-test.2
- project: sdk-core 0.1.1-pipeline-test.3
Contributor
Author
|
Don't forget to cleanup:
|
- project: sdk-core 0.1.1-pipeline-test.4
- project: sdk-core 0.1.1-pipeline-test.5
- project: sdk-core 0.1.1-pipeline-test.6
- project: sdk-core 0.1.1-pipeline-test.7
- project: sdk-core 0.1.1-pipeline-test.8
- project: sdk-core 0.1.1-pipeline-test.9
- project: sdk-core 0.1.1-pipeline-test.10
- project: sdk-core 0.1.1-pipeline-test.11
dm3ch
requested review from
Copilot and
vbrvk
and removed request for
Copilot
There was a problem hiding this comment.
Pull request overview
This PR overhauls the SDK release and publishing pipelines to use NX's built-in release tooling. The workflow consolidates version bumping, changelog generation, and publishing into a single unified pipeline that supports both npmjs and GitHub Packages registries.
Key changes:
- Migrates from custom version bumping to NX release with configurable semver bumps and prerelease support
- Consolidates release and publish workflows into a single pipeline with separate jobs for npmjs and GitHub Packages
- Adds dry-run capability for testing releases without publishing
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/release.yml |
Complete rewrite to use NX release tooling with three jobs: release, publish-npmjs, and publish-github-packages |
.github/workflows/publish.yml |
Removed standalone publish workflow (now integrated into release.yml) |
.github/workflows/test-publish.yml |
Removed dry-run testing workflow (dry-run now built into release.yml) |
nx.json |
Added version, git, and releaseTag configuration for NX release |
typescript/README.md |
Updated release process documentation to reflect new workflow |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- project: sdk-core 0.1.1-pipeline-final-test.0
vbrvk
approved these changes
Nov 26, 2025
dm3ch
commented
Nov 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Summary
What does this PR change?
Introduce pipelines for lib publishing
Related Issue/Ticket:
ITSM-1219
Testing & Verification
How was this tested?
Risk Assessment
Risk Level:
Risks & Impact